[Snyk] Security upgrade @backstage/types from 0.0.0-use.local to 0.1.1#5372
[Snyk] Security upgrade @backstage/types from 0.0.0-use.local to 0.1.1#5372snyk-io[bot] wants to merge 1 commit intomasterfrom
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-TARFS-10293725
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
Reviewer's GuideThis PR applies a Snyk-driven security upgrade by bumping @backstage/types from a workspace reference to version 0.1.1 in plugins/search-common, addressing a high-severity vulnerability, and highlights the need to manually update the yarn.lock file before merging. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) |
![graphite-app[bot]](https://avatars.githubusercontent.com/in/158384?s=60&v=4){kind=small}
| "dependencies": { | ||
| "@backstage/plugin-permission-common": "workspace:^", | ||
| "@backstage/types": "workspace:^" | ||
| "@backstage/types": "0.1.1" |
There was a problem hiding this comment.
This change introduces a dependency inconsistency by replacing the workspace reference with a specific version number. In a monorepo setup where other packages use workspace:^ references, switching just one dependency to a fixed version (0.1.1) breaks the consistency pattern and can lead to versioning problems.
The security vulnerability should be addressed by updating the @backstage/types package within the workspace rather than bypassing the workspace reference. This maintains the monorepo's dependency management approach while still addressing the security concern.
Consider updating the vulnerable dependency in its source location instead of changing how it's referenced here.
| "@backstage/types": "0.1.1" | |
| "@backstage/types": "workspace:^" |
Spotted by Diamond
Is this helpful? React 👍 or 👎 to let us know.
|
This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution! |
Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):
plugins/search-common/package.jsonNote for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the
.yarn/cache/directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to runyarnto update the contents of the./yarn/cachedirectory.If you are not using zero-install you can ignore this as your flow should likely be unchanged.
Vulnerabilities that will be fixed with an upgrade:
SNYK-JS-TARFS-10293725
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Improper Link Resolution Before File Access ('Link Following')
Summary by Sourcery
Bug Fixes: